Conversation
|
📦 Statoscope quick diff with main-branch: ⏱ Build time: 1.5 sec (2.74%) ⚖️ Initial size: 0.31 kb (0.01%) 🕵️ Validation errors: 0 Full Statoscope report could be found here |
|
|
|
|
…actions, update access dialog translations, and enhance invitation types
|
i18n-check |
|
i18n-check |
|
i18n-check Errors occurred when merging changes from your branch with the Weblate branch.Resolve conflicts according to instructions
|
| "toast_switch-publication-status-failed": "Не удалось изменить публичный доступ", | ||
| "toast_switch-publication-status-success": "Публичный доступ был изменен" | ||
| "toast_switch-publication-status-success": "Публичный доступ был изменен", | ||
| "label_public-access-warning-title": "Вы даете доступ ко всем выбранным связанным объектам", |
There was a problem hiding this comment.
There is no code in the opesource repo that uses these keys. Plz add a separate keyset for the new access dialog in the same repo where this keyset are used.
| ResendInvitationRequest, | ||
| } from '../types/invitations'; | ||
|
|
||
| export const organizationManager = { |
There was a problem hiding this comment.
Why should we declare these actions in the opensource repo? We don't use them here.
| federation?: unknown; | ||
| pictureData?: string; | ||
| idpType?: string | null; | ||
| displayName?: string | React.ReactNode; |
There was a problem hiding this comment.
SubjectClaims is used in BatchListMembersResponse, which is used by the schema action as return type. How schema action (fetch request) can return React.ReactNode?
If such model creates in UI, the customized type should be placed in the ui folder (even types). Imports from react should not be used in shared.
| @@ -0,0 +1 @@ | |||
| export type OpenAccessDialog = (arg: any) => void; | |||
|
|
||
| export type AclSubjectProps = { | ||
| subjectClaims: SubjectClaims; | ||
| iconSlot?: React.ReactNode; |
| avatarData?: string; | ||
| } & Omit<SubjectClaims, 'sub' | 'subType'>; | ||
|
|
||
| export interface AclSubjectSelectProps extends Omit<AclSubjectSuggestProps, 'onSubjectChange'> { |
There was a problem hiding this comment.
This component is not related to opensource repo. Is this declared here only because we don't have its own registry in extensions?
|
i18n-check Errors occurred when merging changes from your branch with the Weblate branch.Resolve conflicts according to instructions
|
|
i18n-check Errors occurred when merging changes from your branch with the Weblate branch.Resolve conflicts according to instructions
|
|
i18n-check Errors occurred when merging changes from your branch with the Weblate branch.Resolve conflicts according to instructions
|
| "label_author-description": "При публикации {{subject}} можно указать ссылку на его источник или автора. Ссылка будет отображаться внизу {{subject}}.", | ||
| "label_author-link": "Ссылка", | ||
| "label_author-link-error": "Неверный формат ссылки", | ||
| "label_author-link-required": "Ссылка обязательна при указании автора", |
| </div> | ||
|
|
||
| {showWarning && ( | ||
| <> |
There was a problem hiding this comment.
according to the code style, we use React.Fragment
src/ui/units/collections/components/CollectionContent/hooks/useActions.tsx
Show resolved
Hide resolved
| ResendInvitationRequest, | ||
| } from '../types/invitations'; | ||
|
|
||
| export const organizationManager = { |
| "label_delete": "Удалить", | ||
| "label_to": "Кому", |
There was a problem hiding this comment.
there is also a lack of en, without this the keys will not work correctly
|
i18n-check Errors occurred when merging changes from your branch with the Weblate branch.Resolve conflicts according to instructions
|
| @@ -1 +1,5 @@ | |||
| export type UseSubjectsListId = {type: 'organizationId' | 'cloudId'; id: string | undefined}; | |||
| export type UseSubjectsListId = { | |||
There was a problem hiding this comment.
This type is used to receive the params needed to retrieve a list of subjects. The title is not required for that. Don't mix logic for different purposes.
…/datalens-ui into CHARTS-11939-access-dialog
| dispatch(closeDialog()); | ||
| if (isNewAccessDialogEnabled) { | ||
| openAccessDialog(dispatch, { | ||
| collectionId: item?.collectionId ?? undefined, |
There was a problem hiding this comment.
item can be optional here?
| dispatch(closeDialog()); | ||
| if (isNewAccessDialogEnabled) { | ||
| openAccessDialog(dispatch, { | ||
| workbookId: item?.workbookId ?? undefined, |
There was a problem hiding this comment.
item can be optional here?
| openDialog({ | ||
| id: DIALOG_ACCESS, | ||
| props: { | ||
| workbookId: workbook?.workbookId ?? undefined, |
There was a problem hiding this comment.
workbook can be optional here?
No description provided.